Skip to content

Point the roadmap reference at the org template - #38

Open
rahlk wants to merge 1 commit into
mainfrom
feat/roadmap-template-pointer
Open

Point the roadmap reference at the org template#38
rahlk wants to merge 1 commit into
mainfrom
feat/roadmap-template-pointer

Conversation

@rahlk

@rahlk rahlk commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Follow-up to codellm-devkit/.github#33.

Motivation and Context

The roadmap skeleton lived as prose inside a fenced code block in this skill's reference file. It wasn't copyable, wasn't where the artifact lands, and its editorial phrasing ("The list that makes the rest mean something") shipped into every roadmap derived from it.

The template now lives in codellm-devkit/.githubdocs/design/roadmap-template.md, beside ISSUE_TEMPLATE/ and CONTRIBUTING.md — the same split issue bodies already use: org repo owns the shape, the skill owns when and why.

Reference drops 63 → 19 lines: a link plus the four rules that are genuinely skill-side (one roadmap amended in place; rows are contract decisions not themes; Starting now holds exactly one; dropped candidates move to Not now with a reason).

The mode itself is unchanged — planning-cldk-work, its loop, gate and scenarios all stay.

How Has This Been Tested?

  • check-readme-dispatcher-sync.sh green.
  • Release-notes extraction for 0.4.1 returns the section.
  • Scenario specs unchanged and still not executable.

Breaking Changes

No. The reference points elsewhere; no behaviour, routing or gate changes.

Depends on codellm-devkit/.github#33 — merge that first, or this links a file that does not exist yet.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the Codellm-Devkit Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally — consistency check green
  • I have added appropriate error handling — n/a
  • I have added or updated documentation as needed

Additional context

Patch bump to 0.4.1 — no behaviour change, so not a minor.

The skeleton was prose in a fenced block here: not copyable, not where the artifact
lands, and its editorial phrasing shipped into every roadmap made from it.

Template now lives in codellm-devkit/.github next to the issue forms
(codellm-devkit/.github#33), on the same principle issue bodies already follow --
org repo owns the shape, skill owns when and why. Reference drops from 63 lines to
19: a link plus the four rules that are genuinely skill-side.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant